Implemented the retry policy engine - #405
Merged
Lakes41 merged 4 commits intoAug 30, 2026
Merged
Conversation
…y comparing original values.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
Implemented a generic asynchronous retry engine for GuildPass Core that provides configurable exponential backoff, jitter, cancellation, and caller-defined retry classification. This standalone resilience primitive can be adopted by future integrations (Stellar RPC, internal services, event processors) without depending on those services today.
Linked Issue
Closes #370
Type of Change
Changes Made
@guildpass/retry-policy- A standalone retry engine with no dependencies on Stellar RPC, HTTP clients, Redis, Prisma, or other servicesTest Evidence
pnpm --filter @guildpass/retry-policy testOutput:
Smart Contract Checklist (complete if ⛓️ checked above)
N/A - This is a TypeScript package, not a smart contract
General Checklist
npm run typecheckpasses (orpnpm typecheck)npm run lintpasses (N/A - no linting configured for this package)npm run testpasses — all tests green (orpnpm test).env.exampleupdated if new env variables were added (N/A - no env variables)Additional Notes
causeand includes attempt count